Method for decoding a service guide

ABSTRACT

The invention is: A method for decoding a service guide associated with a video bitstream comprising: (a) receiving a content fragment within the service guide, (b) receiving a name element within the content fragment, (c) receiving a description element within the content fragment and (d) decoding the service guide.

TECHNICAL FIELD

The present disclosure relates generally to a service guide.

BACKGROUND ART

A broadcast service is capable of being received by all users havingbroadcast receivers. Broadcast services can be roughly divided into twocategories, namely, a radio broadcast service carrying only audio and amultimedia broadcast service carrying audio, video and data. Suchbroadcast services have developed from analog services to digitalservices. More recently, various types of broadcasting systems (such asa cable broadcasting system, a satellite broadcasting system, anInternet based broadcasting system, and a hybrid broadcasting systemusing both a cable network, Internet, and/or a satellite) provide highquality audio and video broadcast services along with a high-speed dataservice. Also, broadcast services include sending and/or receivingaudio, video, and/or data directed to an individual computer and/orgroup of computers and/or one or more mobile communication devices.

SUMMARY OF INVENTION Technical Problem

In addition to more traditional stationary receiving devices, mobilecommunication devices are likewise configured to support such services.Such configured mobile devices have facilitated users to use suchservices while on the move, such as mobile phones. An increasing needfor multimedia services has resulted in various wireless/broadcastservices for both mobile communications and general wire communications.Further, this convergence has merged the environment for different wireand wireless broadcast services.

Open Mobile Alliance (OMA), is a standard for interworking betweenindividual mobile solutions, serves to define various applicationstandards for mobile software and Internet services. OMA MobileBroadcast Services Enabler Suite (OMA BCAST) is a specification designedto support mobile broadcast technologies. The OMA BCAST definestechnologies that provide IP-based mobile content delivery, whichincludes a variety of functions such as a service guide, downloading andstreaming, service and content protection, service subscription, androaming.

Solution to Problem

According to the present invention, there is provided a method fordecoding a service guide associated with a video bitstream comprising:

(a) receiving a content fragment within the service guide;

(b) receiving a name element within the content fragment,

wherein the name element is an extended name element which includessub-elements to indicate name and phonetic information about the nameelement, the name element contains the sub-elements including a firstSpeechInfoURI element and a first SpeechInfo element, and the nameelement includes a first text attribute which is a name of a servicewith a data type of string,

wherein the first SpeechInfoURI element is a URI address where a firstSpeechInfo object for the name element is acquired, and the firstSpeechInfoURI element includes a first content-type attribute and afirst content-enc attribute, wherein the first content-type is acontent-type of the first SpeechInfo object referenced by the firstSpeechInfoURI element and the first content-enc is a content encoding ofthe first SpeechInfo object referenced by the first SpeechInfoURIelement, and

wherein the first SpeechInfo element is embedded speech informationobject for the name element, and the first Speech Info element includesa second content-type attribute and a second content-enc attribute,wherein the second content-type is a content-type of the firstSpeechInfo object and the second content-enc is a content encoding ofthe second SpeechInfo object,

(c) receiving a description element within the content fragment;

wherein the description element is an extended description element whichincludes sub-elements to indicate description and phonetic informationabout the description element, the description element contains thesub-elements including a second SpeechInfoURI element and a secondSpeechInfo element, and the description element includes a second textattribute which is a description of the service with a data type ofstring,

wherein the second SpeechInfoURI element is a URI address where a secondSpeechInfo object for the description element is acquired, and thesecond SpeechInfoURI element includes a third content-type attribute anda third content-enc attribute, wherein the third content-type is acontent-type of the third SpeechInfo object referenced by the secondSpeechInfoURI element and the third content-enc is a content encoding ofthe third SpeechInfo object referenced by the second SpeechInfoURIelement, and

wherein the second SpeechInfo element is embedded speech informationobject for the description element, and the second SpeechInfo elementincludes a fourth content-type attribute and a fourth content-encattribute, wherein the fourth content-type is a content-type of a fourthSpeechInfo object and the fourth content-enc is a content encoding ofthe fourth SpeechInfo object,

(d) decoding the service guide.

According to the present invention, there is provided a decoder fordecoding a service guide associated with a video bitstream comprising:

a receiver configured to receive a content fragment within the serviceguide, a name element within the content fragment and a descriptionelement within the content fragment,

wherein the name element is an extended name element which includessub-elements to indicate name and phonetic information about the nameelement, the name element contains the sub-elements including a firstSpeechInfoURI element and a first SpeechInfo element, and the nameelement includes a first text attribute which is a name of a servicewith a data type of string,

wherein the first SpeechInfoURI element is a URI address where a firstSpeechInfo object for the name element is acquired, and the firstSpeechInfoURI element includes a first content-type attribute and afirst content-enc attribute, wherein the first content-type is acontent-type of the first SpeechInfo object referenced by the firstSpeechInfoURI element and the first content-enc is a content encoding ofthe first SpeechInfo object referenced by the first SpeechInfoURIelement, and

wherein the first SpeechInfo element is embedded speech informationobject for the name element, and the first Speech Info element includesa second content-type attribute and a second content-enc attribute,wherein the second content-type is a content-type of the firstSpeechInfo object and the second content-enc is a content encoding ofthe second SpeechInfo object,

wherein the description element is an extended description element whichincludes sub-elements to indicate description and phonetic informationabout the description element, the description element contains thesub-elements including a second SpeechInfoURI element and a secondSpeechInfo element, and the description element includes a second textattribute which is a description of the service with a data type ofstring,

wherein the second SpeechInfoURI element is a URI address where a secondSpeechInfo object for the description element is acquired, and thesecond SpeechInfoURI element includes a third content-type attribute anda third content-enc attribute, wherein the third content-type is acontent-type of the third SpeechInfo object referenced by the secondSpeechInfoURI element and the third content-enc is a content encoding ofthe third SpeechInfo object referenced by the second SpeechInfoURIelement, and

wherein the second SpeechInfo element is embedded speech informationobject for the description element, and the second SpeechInfo elementincludes a fourth content-type attribute and a fourth content-encattribute, wherein the fourth content-type is a content-type of a fourthSpeechInfo object and the fourth content-enc is a content encoding ofthe fourth SpeechInfo object, and

the decoder is configured to decode the service guide.

Advantageous Effects of Invention

The foregoing and other objectives, features, and advantages of theinvention will be more readily understood upon consideration of thefollowing detailed description of the invention, taken in conjunctionwith the accompanying drawings.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating logical architecture of a BCASTsystem specified by OMA BCAST working group in an application layer anda transport layer.

FIG. 2 is a diagram illustrating a structure of a service guide for usein the OMA BCAST system.

FIG. 2A is a diagram showing cardinalities and reference directionbetween service guide fragments.

FIG. 3 is a block diagram illustrating a principle of the conventionalservice guide delivery method.

FIG. 4 illustrates description scheme.

FIG. 5 illustrates elements and attributes for speech/phoneticinformation.

FIG. 5A illustrates elements and attributes for speech/phoneticinformation.

FIG. 6 illustrates speech information URI element in service guide.

FIG. 7 illustrates speech information object element in service guide.

FIG. 8 illustrates speech information URI element and speech informationobject in service guide.

FIG. 9 illustrates elements and attributes for speech/phoneticinformation.

FIG. 9A illustrates elements and attributes for speech/phoneticinformation.

FIG. 10 illustrates structure of an exemplary XML schema.

FIG. 11 illustrates structure of an exemplary XML schema.

FIG. 12 illustrates structure of an exemplary XML schema.

FIG. 13 illustrates structure of an exemplary XML schema.

DESCRIPTION OF EMBODIMENTS

Referring to FIG. 1, a logical architecture of a broadcast systemspecified by OMA (Open Mobile Alliance) BCAST may include an applicationlayer and a transport layer. The logical architecture of the BCASTsystem may include a Content Creation (CC) 101, a BCAST ServiceApplication 102, a BCAST Service Distribution/Adaptation (BSDA) 103, aBCAST Subscription Management (BSM) 104, a Terminal 105, a BroadcastDistribution System (BDS) Service Distribution 111, a BDS 112, and anInteraction Network 113. It is to be understood that the broadcastsystem and/or receiver system may be reconfigured, as desired. It is tobe understood that the broadcast system and/or receiver system mayinclude additional elements and/or fewer elements, as desired.

In general, the Content Creation (CC) 101 may provide content that isthe basis of BCAST services. The content may include files for commonbroadcast services, e.g., data for a movie including audio and video.The Content Creation 101 provides a BCAST Service Application 102 withattributes for the content, which are used to create a service guide andto determine a transmission bearer over which the services will bedelivered.

In general, the BCAST Service Application 102 may receive data for BCASTservices provided from the Content Creation 101, and converts thereceived data into a form suitable for providing media encoding, contentprotection, interactive services, etc. The BCAST Service Application 102provides the attributes for the content, which is received from theContent Creation 101, to the BSDA 103 and the BSM 104.

In general, the BSDA 103 may perform operations, such as file/streamingdelivery, service gathering, service protection, service guidecreation/delivery and service notification, using the BCAST service dataprovided from the BCAST Service Application 102. The BSDA 103 adapts theservices to the BDS 112.

In general, the BSM 104 may manage, via hardware or software, serviceprovisioning, such as subscription and charging-related functions forBCAST service users, information provisioning used for BCAST services,and mobile terminals that receive the BCAST services.

In general, the Terminal 105 may receive content/service guide andprogram support information, such as content protection, and provides abroadcast service to a user. The BDS Service Distribution 111 deliversmobile broadcast services to a plurality of terminals through mutualcommunication with the BDS 112 and the Interaction Network 113.

In general, the BDS 112 may deliver mobile broadcast services over abroadcast channel, and may include, for example, a Multimedia BroadcastMulticast Service (MBMS) by 3rd Generation Project Partnership (3GPP), aBroadcast Multicast Service (BCMCS) by 3rd Generation ProjectPartnership 2 (3GPP2), a DVB-Handheld (DVB-H) by Digital VideoBroadcasting (DVB), or an Internet Protocol (IP) based broadcastingcommunication network. The Interaction Network 113 provides aninteraction channel, and may include, for example, a cellular network.

The reference points, or connection paths between the logical entitiesof FIG. 1, may have a plurality of interfaces, as desired. Theinterfaces are used for communication between two or more logicalentities for their specific purposes. A message format, a protocol andthe like are applied for the interfaces. In some embodiments, there areno logical interfaces between one or more different functions.

BCAST-1 121 is a transmission path for content and content attributes,and BCAST-2 122 is a transmission path for a content-protected orcontent-unprotected BCAST service, attributes of the BCAST service, andcontent attributes.

BCAST-3 123 is a transmission path for attributes of a BCAST service,attributes of content, user preference/subscription information, a userrequest, and a response to the request. BCAST-4 124 is a transmissionpath for a notification message, attributes used for a service guide,and a key used for content protection and service protection.

BCAST-5 125 is a transmission path for a protected BCAST service, anunprotected BCAST service, a content-protected BCAST service, acontent-unprotected BCAST service, BCAST service attributes, contentattributes, a notification, a service guide, security materials such asa Digital Right Management (DRM) Right Object (RO) and key values usedfor BCAST service protection, and all data and signaling transmittedthrough a broadcast channel.

BCAST-6 126 is a transmission path for a protected BCAST service, anunprotected BCAST service, a content-protected BCAST service, acontent-unprotected BCAST service, BCAST service attributes, contentattributes, a notification, a service guide, security materials such asa DRM RO and key values used for BCAST service protection, and all dataand signaling transmitted through an interaction channel.

BCAST-7 127 is a transmission path for service provisioning,subscription information, device management, and user preferenceinformation transmitted through an interaction channel for controlinformation related to receipt of security materials, such as a DRM ROand key values used for BCAST service protection.

BCAST-8 128 is a transmission path through which user data for a BCASTservice is provided. BDS-1 129 is a transmission path for a protectedBCAST service, an unprotected BCAST service, BCAST service attributes,content attributes, a notification, a service guide, and securitymaterials, such as a DRM RO and key values used for BCAST serviceprotection.

BDS-2 130 is a transmission path for service provisioning, subscriptioninformation, device management, and security materials, such as a DRM ROand key values used for BCAST service protection.

X-1 131 is a reference point between the BDS Service Distribution 111and the BDS 112. X-2 132 is a reference point between the BDS ServiceDistribution 111 and the Interaction Network 113. X-3 133 is a referencepoint between the BDS 112 and the Terminal 105. X-4 134 is a referencepoint between the BDS Service Distribution 111 and the Terminal 105 overa broadcast channel. X-5 135 is a reference point between the BDSService Distribution 111 and the Terminal 105 over an interactionchannel. X-6 136 is a reference point between the Interaction Network113 and the Terminal 105.

Referring to FIG. 2, an exemplary service guide for the OMA BCAST systemis illustrated. For purposes of illustration, the solid arrows betweenfragments indicate the reference directions between the fragments. It isto be understood that the service guide system may be reconfigured, asdesired. It is to be understood that the service guide system mayinclude additional elements and/or fewer elements, as desired. It is tobe understood that functionality of the elements may be modified and/orcombined, as desired.

FIG. 2A is a diagram showing cardinalities and reference directionbetween service guide fragments. The meaning of the cardinalities shownin the FIG. 2 is the following: One instantiation of Fragment A as inFIG. 2A references c to d instantiations of Fragment B. If c=d, d isomitted. Thus, if c>0 and Fragment A exists, at least c instantiation ofFragment B must also exist, but at most d instantiations of Fragment Bmay exist. Vice versa, one instantiation of Fragment B is referenced bya to b instantiations of Fragment A. If a=b, b is omitted. The arrowconnection from Fragment A pointing to Fragment B indicates thatFragment A contains the reference to Fragment B.

With respect to FIG. 2, in general, the service guide may include anAdministrative Group 200 for providing basic information about theentire service guide, a Provisioning Group 210 for providingsubscription and purchase information, a Core Group 220 that acts as acore part of the service guide, and an Access Group 230 for providingaccess information that control access to services and content.

The Administrative Group 200 may include a Service Guide DeliveryDescriptor (SGDD) block 201. The Provision Group 210 may include aPurchase Item block 211, a Purchase Data block 212, and a PurchaseChannel block 213. The Core Group 220 may include a Service block 221, aSchedule block 222, and a Content block 223. The Access Group 230 mayinclude an Access block 231 and a Session Description block 232.

The service guide may further include Preview Data 241 and InteractivityData 251 in addition to the four information groups 200, 210, 220, and230.

The aforementioned components may be referred to as basic units orfragments constituting aspects of the service guide, for purposes ofidentification.

The SGDD fragment 201 may provide information about a delivery sessionwhere a Service Guide Delivery Unit (SGDU) is located. The SGDU is acontainer that contains service guide fragments 211, 212, 213, 221, 222,223, 231, 232, 241, and 251, which constitute the service guide. TheSGDD may also provide the information on the entry points for receivingthe grouping information and notification messages.

The Service fragment 221, which is an upper aggregate of the contentincluded in the broadcast service, may include information on servicecontent, genre, service location, etc. In general, the ‘Service’fragment describes at an aggregate level the content items whichcomprise a broadcast service. The service may be delivered to the userusing multiple means of access, for example, the broadcast channel andthe interactive channel. The service may be targeted at a certain usergroup or geographical area. Depending on the type of the service it mayhave interactive part(s), broadcast-only part(s), or both. Further, theservice may include components not directly related to the content butto the functionality of the service such as purchasing or subscriptioninformation. As the part of the Service Guide, the ‘Service’ fragmentforms a central hub referenced by the other fragments including‘Access’, ‘Schedule’, ‘Content’ and ‘PurchaseItem’ fragments. Inaddition to that, the ‘Service’ fragment may reference ‘PreviewData’fragment. It may be referenced by none or several of each of thesefragments. Together with the associated fragments the terminal maydetermine the details associated with the service at any point of time.These details may be summarized into a user-friendly display, forexample, of what, how and when the associated content may be consumedand at what cost.

The Access fragment 231 may provide access-related information forallowing the user to view the service and delivery method, and sessioninformation associated with the corresponding access session. As such,the ‘Access’ fragment describes how the service may be accessed duringthe lifespan of the service. This fragment contains or referencesSession Description information and indicates the delivery method. Oneor more ‘Access’ fragments may reference a ‘Service’ fragment, offeringalternative ways for accessing or interacting with the associatedservice. For the Terminal, the ‘Access’ fragment provides information onwhat capabilities are required from the terminal to receive and renderthe service. The ‘Access’ fragment provides Session Descriptionparameters either in the form of inline text, or through a pointer inthe form of a URI to a separate Session Description. Session Descriptioninformation may be delivered over either the broadcast channel or theinteraction channel.

The Session Description fragment 232 may be included in the Accessfragment 231, and may provide location information in a Uniform ResourceIdentifier (URI) form so that the terminal may detect information on theSession Description fragment 232. The Session Description fragment 232may provide address information, codec information, etc., aboutmultimedia content existing in the session. As such, the‘SessionDescription’ is a Service Guide fragment which provides thesession information for access to a service or content item. Further,the Session Description may provide auxiliary description information,used for associated delivery procedures. The Session Descriptioninformation is provided using either syntax of SDP in text format, orthrough a 3GPP MBMS User Service Bundle Description [3GPP TS 26.346](USBD). Auxiliary description information is provided in XML format andcontains an Associated Delivery Description as specified in[BCAST10-Distribution]. Note that in case SDP syntax is used, analternative way to deliver the Session Description is by encapsulatingthe SDP in text format in ‘Access’ fragment. Note that SessionDescription may be used both for Service Guide delivery itself as wellas for the content sessions.

The Purchase Item fragment 211 may provide a bundle of service, content,time, etc., to help the user subscribe to or purchase the Purchase Itemfragment 211. As such, the ‘PurchaseItem’ fragment represents a group ofone or more services (i.e. a service bundle) or one or more contentitems, offered to the end user for free, for subscription and/orpurchase. This fragment can be referenced by ‘PurchaseData’ fragment(s)offering more information on different service bundles. The‘PurchaseItem’ fragment may be also associated with: (1) a ‘Service’fragment to enable bundled services subscription and/or, (2) a‘Schedule’ fragment to enable consuming a certain service or content ina certain timeframe (pay-per-view functionality) and/or, (3) a ‘Content’fragment to enable purchasing a single content file related to aservice, (4) other ‘PurchaseItem’ fragments to enable bundling ofpurchase items.

The Purchase Data fragment 212 may include detailed purchase andsubscription information, such as price information and promotioninformation, for the service or content bundle. The Purchase Channelfragment 213 may provide access information for subscription orpurchase. As such, the main function of the ‘PurchaseData’ fragment isto express all the available pricing information about the associatedpurchase item. The ‘PurchaseData’ fragment collects the informationabout one or several purchase channels and may be associated withPreviewData specific to a certain service or service bundle. It carriesinformation about pricing of a service, a service bundle, or, a contentitem. Also, information about promotional activities may be included inthis fragment. The SGDD may also provide information regarding entrypoints for receiving the service guide and grouping information aboutthe SGDU as the container.

The Preview Data fragment 241 may be used to provide preview informationfor a service, schedule, and content. As such, ‘PreviewData’ fragmentcontains information that is used by the terminal to present the serviceor content outline to users, so that the users can have a general ideaof what the service or content is about. ‘PreviewData’ fragment caninclude simple texts, static images (for example, logo), short videoclips, or even reference to another service which could be a low bitrate version for the main service. ‘Service’, ‘Content’, ‘PurchaseData’,‘Access’ and ‘Schedule’ fragments may reference ‘PreviewData’ fragment.

The Interactivity Data fragment 251 may be used to provide aninteractive service according to the service, schedule, and contentduring broadcasting. More detailed information about the service guidecan be defined by one or more elements and attributes of the system. Assuch, the InteractivityData contains information that is used by theterminal to offer interactive services to the user, which is associatedwith the broadcast content. These interactive services enable users toe.g. vote during TV shows or to obtain content related to the broadcastcontent. ‘InteractivityData’ fragment points to one or many‘InteractivityMedia’ documents that include xhtml files, static images,email template, SMS template, MMS template documents, etc. The‘InteractivityData’ fragment may reference the ‘Service’, ‘Content’ and‘Schedule’ fragments, and may be referenced by the ‘Schedule’ fragment.

The ‘Schedule’ fragment defines the timeframes in which associatedcontent items are available for streaming, downloading and/or rendering.This fragment references the ‘Service’ fragment. If it also referencesone or more ‘Content’ fragments or ‘InterativityData’ fragments, then itdefines the valid distribution and/or presentation timeframe of thosecontent items belonging to the service, or the valid distributiontimeframe and the automatic activation time of theInteractivityMediaDocuments associated with the service. On the otherhand, if the ‘Schedule’ fragment does not reference any ‘Content’fragment(s) or ‘InteractivityData’ fragment(s), then it defines thetimeframe of the service availability which is unbounded.

The ‘Content’ fragment gives a detailed description of a specificcontent item. In addition to defining a type, description and languageof the content, it may provide information about the targeted user groupor geographical area, as well as genre and parental rating. The‘Content’ fragment may be referenced by Schedule, PurchaseItem or‘InteractivityData’ fragment. It may reference ‘PreviewData’ fragment or‘Service’ fragment.

The ‘PurchaseChannel’ fragment carries the information about the entityfrom which purchase of access and/or content rights for a certainservice, service bundle or content item may be obtained, as defined inthe ‘PurchaseData’ fragment. The purchase channel is associated with oneor more Broadcast Subscription Managements (BSMs). The terminal is onlypermitted to access a particular purchase channel if it is affiliatedwith a BSM that is also associated with that purchase channel. Multiplepurchase channels may be associated to one ‘PurchaseData’ fragment. Acertain end-user can have a “preferred” purchase channel (e.g. his/hermobile operator) to which all purchase requests should be directed. Thepreferred purchase channel may even be the only channel that an end-useris allowed to use.

The ServiceGuideDeliveryDescriptor is transported on the Service GuideAnnouncement Channel, and informs the terminal the availability,metadata and grouping of the fragments of the Service Guide in theService Guide discovery process. A SGDD allows quick identification ofthe Service Guide fragments that are either cached in the terminal orbeing transmitted. For that reason, the SGDD is preferably repeated ifdistributed over broadcast channel. The SGDD also provides the groupingof related Service Guide fragments and thus a means to determinecompleteness of such group. The ServiceGuideDeliveryDescriptor isespecially useful if the terminal moves from one service coverage areato another. In this case, the ServiceGuideDeliveryDescriptor can be usedto quickly check which of the Service Guide fragments that have beenreceived in the previous service coverage area are still valid in thecurrent service coverage area, and therefore don't have to be re-parsedand re-processed.

Although not expressly depicted, the fragments that constitute theservice guide may include element and attribute values for fulfillingtheir purposes. In addition, one or more of the fragments of the serviceguide may be omitted, as desired. Also, one or more fragments of theservice guide may be combined, as desired. Also, different aspects ofone or more fragments of the service guide may be combined together,re-organized, and otherwise modified, or constrained as desired.

Referring to FIG. 3, an exemplary block diagram illustrates aspects of aservice guide delivery technique. The Service Guide Deliver Descriptorfragment 201 may include the session information, grouping information,and notification message access information related to all fragmentscontaining service information. When the mobile broadcastservice-enabled terminal 105 turns on or begins to receive the serviceguide, it may access a Service Guide Announcement Channel (SGAnnouncement Channel) 300.

The SG Announcement Channel 300 may include at least one of SGDD 200(e.g., SGDD #1, . . . , SGDD #2, SGDD #3), which may be formatted in anysuitable format, such as that illustrated in Service Guide for MobileBroadcast Services, Open Mobile Alliance, Version 1.0.1, Jan. 9, 2013and/or Service Guide for Mobile Broadcast Services, open MobileAlliance, Version 1.1, Oct. 29, 3013; both of which are incorporated byreference in their entirety. The descriptions of elements and attributesconstituting the Service Guide Delivery Descriptor fragment 201 may bereflected in any suitable format, such as for example, a table formatand/or in an eXtensible Markup Language (XML) schema.

The actual data is preferably provided in XML format according to theSGDD fragment 201. The information related to the service guide may beprovided in various data formats, such as binary, where the elements andattributes are set to corresponding values, depending on the broadcastsystem.

The terminal 105 may acquire transport information about a Service GuideDelivery Unit (SGDU) 312 containing fragment information from aDescriptorEntry of the SGDD fragment received on the SG AnnouncementChannel 300.

The DescriptorEntry 302, which may provide the grouping information of aService Guide includes the “GroupingCriteria”,“ServiceGuideDeliveryUnit”, “Transport”, and AlternativeAccessURI”. Thetransport-related channel information may be provided by the “Transport”or “AlternativeAccessURI”, and the actual value of the correspondingchannel is provided by “ServiceGuideDeliveryUnit”. Also, upper layergroup information about the SGDU 312, such as “Service” and “Genre”, maybe provided by “GroupingCriteria”. The terminal 105 may receive andpresent all of the SGDUs 312 to the user according to the correspondinggroup information.

Once the transport information is acquired, the terminal 105 may accessall of the Delivery Channels acquired from a DescriptorEntry 302 in anSGDD 301 on an SG Delivery Channel 310 to receive the actual SGDU 312.The SG Delivery Channels can be identified using the “GroupingCriteria”.In the case of time grouping, the SGDU can be transported with atime-based transport channel such as an Hourly SG Channel 311 and aDaily SG Channel. Accordingly, the terminal 105 can selectively accessthe channels and receive all the SGDUs existing on the correspondingchannels. Once the entire SGDU is completely received on the SG DeliveryChannels 310, the terminal 105 checks all the fragments contained in theSGDUs received on the SG Delivery Channels 310 and assembles thefragments to display an actual full service guide 320 on the screenwhich can be subdivided on an hourly basis 321.

In the conventional mobile broadcast system, the service guide isformatted and transmitted such that only configured terminals receivethe broadcast signals of the corresponding broadcast system. Forexample, the service guide information transmitted by a DVB-H system canonly be received by terminals configured to receive the DVB-H broadcast.

The service providers provide bundled and integrated services usingvarious transmission systems as well as various broadcast systems inaccordance with service convergence, which may be referred to asmultiplay services. The broadcast service providers may also providebroadcast services on IP networks. Integrated service guidetransmission/reception systems may be described using terms of entitiesdefined in the 3GPP standards and OMA BCAST standards (e.g., a scheme).However, the service guide/reception systems may be used with anysuitable communication and/or broadcast system.

Referring to FIG. 4, the scheme may include, for example, (1) Name; (2)Type; (3) Category; (4) Cardinality; (5) Description; and (6) Data type.The scheme may be arranged in any manner, such as a table format of anXML format.

The “name” column indicates the name of an element or an attribute. The“type” column indicates an index representing an element or anattribute. An element can be one of E1, E2, E3, E4, . . . , E[n]. E1indicates an upper element of an entire message, E2 indicates an elementbelow the E1, E3 indicates an element below E2, E4 indicates an elementbelow the E3, and so forth. An attribute is indicated by A. For example,an “A” below E1 means an attribute of element E1. In some cases thenotation may mean the following E=Element, A=Attribute, E1=sub-element,E2=sub-element's sub-element, E[n]=sub-element of element[n−1]. The“category” column is used to indicate whether the element or attributeis mandatory. If an element is mandatory, the category of the element isflagged with an “M”. If an element is optional, the category of theelement is flagged with an “0”. If the element is optional for networkto support it the element is flagged with a “NO”. If the element ismandatory for terminal to support it is flagged with a TM. If theelement is mandatory for network to support it the element is flaggedwith “NM”. If the element is optional for terminal to support it theelement is flagged with “TO”. If an element or attribute has cardinalitygreater than zero, it is classified as M or NM to maintain consistency.The “cardinality” column indicates a relationship between elements andis set to a value of 0, 0 . . . 1, 1, 0 . . . n, and 1 . . . n. 0indicates an option, 1 indicates a necessary relationship, and nindicates multiple values. For example, 0 . . . n means that acorresponding element can have no or n values. The “description” columndescribes the meaning of the corresponding element or attribute, and the“data type” column indicates the data type of the corresponding elementor attribute.

A service may represent a bundle of content items, which forms a logicalgroup to the end-user. An example would be a TV channel, composed ofseveral TV shows. A ‘Service’ fragment contains the metadata describingthe Mobile Broadcast service. It is possible that the same metadata(i.e., attributes and elements) exist in the ‘Content’ fragment(s)associated with that ‘Service’ fragment. In that situation, for thefollowing elements: ‘ParentalRating’, ‘TargetUserProfile’, ‘Genre’ and‘BroadcastArea’, the values defined in ‘Content’ fragment takeprecedence over those in ‘Service’ fragment.

The program guide elements of this fragment may be grouped between theStart of program guide and end of program guide cells in a fragment.This localization of the elements of the program guide reduces thecomputational complexity of the receiving device in arranging aprogramming guide. The program guide elements are generally used foruser interpretation. This enables the content creator to provide userreadable information about the service. The terminal should use alldeclared program guide elements in this fragment for presentation to theend-user. The terminal may offer search, sort, etc. functionalities. TheProgram Guide may consist of the following service elements: (1) Name;(2) Description; (3) AudioLanguage; (4) TextLanguage; (5)ParentalRating; (6) TargetUserProfile; and (7) Genre.

The “Name” element may refer to Name of the Service, possibly inmultiple languages. The language may be expressed using built-in XMLattribute ‘xml:lang’.

The “Description” element may be in multiple languages and may beexpressed using built-in XML attribute ‘xml:lang’.

The “AudioLanguage” element may declare for the end users that thisservice is available with an audio track corresponding to the languagerepresented by the value of this element. The textual value of thiselement can be made available for the end users in different languages.In such a case the language used to represent the value of this elementmay be signaled using the built-in XML attribute ‘xml:lang’, and mayinclude multi-language support. The AudioLanguage may contain anattribute languageSDPTag.

The “languageSDPTag” attribute is an identifier of the audio languagedescribed by the parent ‘AudioLanguage’ element as used in the mediasections describing the audio track in a Session Description. Each‘AudioLanguage’ element declaring the same audio stream may have thesame value of the languageSDPTag′.

The “TextLanguage” element may declare for the end user that the textualcomponents of this service are available in the language represented bythe value of this element. The textual components can be, for instance,a caption or a sub-title track. The textual value of this element can bemade available for the end users in different languages. In such a casethe language used to represent the value of this element may be signaledusing the built-in XML attribute ‘xml:lang’, and may includemulti-language support. The same rules and constraints as specified forthe element ‘AudioLanguage’ of assigning and interpreting the attributeslanguageSDPTag′ and ‘xml:lang’ may be applied for this element.

The “languageSDPTag” attribute is an identifier of the text languagedescribed by the parent ‘TextLanguage’ element as used in the mediasections describing the textual track in a Session Description.

The “ParentalRating” element may declare criteria parents and might beused to determine whether the associated item is suitable for access bychildren, defined according to the regulatory requirements of theservice area. The terminal may support ‘ParentalRating’ being a freestring, and the terminal may support the structured way to express theparental rating level by using the ‘ratingSystem’ and ‘ratingValueName’attributes.

The “ratingSystem” attribute may specify the parental rating system inuse, in which context the value of the ‘ParentalRating’ element issemantically defined. This allows terminals to identify the ratingsystem in use in a non-ambiguous manner and act appropriately. Thisattribute may be instantiated when a rating system is used. Absence ofthis attribute means that no rating system is used (i.e. the value ofthe ‘ParentalRating’ element is to be interpreted as a free string).

The “ratingValueName” attribute may specify the human-readable name ofthe rating value given by this ParentalRating element.

The “TargetUserProfile” may specify elements of the users whom theservice is targeting at. The detailed personal attribute names and thecorresponding values are specified by attributes of ‘attributeName’ an‘attributeValue’. Amongst the possible profile attribute names are age,gender, occupation, etc. (subject to national/local rules & regulations,if present and as applicable regarding use of personal profilinginformation and personal data privacy). The extensible list of‘attributeName’ and ‘attributeValue’ pairs for a particular serviceenables end user profile filtering and end user preference filtering ofbroadcast services. The terminal may be able to support‘TargetUserProfile’ element. The use of ‘TargetUserProfile’ element maybe an “opt-in” capability for users. Terminal settings may allow usersto configure whether to input their personal profile or preference andwhether to allow broadcast service to be automatically filtered based onthe users' personal attributes without users' request. This element maycontain the following attributes: attributeName and attributeValue.

The “attributeName” attribute may be a profile attribute name.

The “attributeValue” attribute may be a profile attribute value.

The “Genre” element may specify classification of service associatedwith characteristic form (e.g. comedy, drama). The OMA BCAST ServiceGuide may allow describing the format of the Genre element in theService Guide in two ways. The first way is to use a free string. Thesecond way is to use the “href” attributes of the Genre element toconvey the information in the form of a controlled vocabulary(classification scheme as defined in [TVA-Metadata] or classificationlist as defined in [MIGFG]). The built-in XML attribute xml:lang may beused with this element to express the language. The network mayinstantiate several different sets of ‘Genre’ element, using it as afree string or with a ‘href’ attribute. The network may ensure thedifferent sets have equivalent and nonconflicting meaning, and theterminal may select one of the sets to interpret for the end-user. The‘Genre’ element may contain the following attributes: type and href.

The “type” attribute may signal the level of the ‘Genre’ element, suchas with the values of “main”, “second”, and “other”.

The “href” attribute may signal the controlled vocabulary used in the‘Genre’ element.

After reviewing the set of programming guide elements and attributes;(1) Name; (2) Description; (3) AudioLanguage; (4) TextLanguage; (5)ParentalRating; (6) TargetUserProfile; and (7) Genre it was determinedthat the receiving device still may have insufficient informationdefined within the programming guide to appropriately render theinformation in a manner suitable for the viewer. In particular, thetraditional NTSC television stations typically have numbers such as, 2,4, 6, 8, 12, and 49. For digital services, program and systeminformation protocol includes a virtual channel table that, forterrestrial broadcasting defines each digital television service with atwo-part number consisting of a major channel followed by a minorchannel. The major channel number is usually the same as the NTSCchannel for the station, and the minor channels have numbers dependingon how many digital television services are present in the digitaltelevision multiples, typically starting at 1. For example, the analogtelevision channel 9, WUSA-TV in Washington, D.C., may identify its twoover-the-air digital services as follows: channel 9-1 WUSA-DT andchannel 9-2 9-Radar. This notation for television channels is readilyunderstandable by a viewer, and the programming guide elements mayinclude this capability as an extension to the programming guide so thatthe information may be computationally efficiently processed by thereceiving device and rendered to the viewer.

For many systems, it is desirable to include the capability toeffectively provide blind or visually impaired persons the ability tomore readily access video programming for a wide variety of videodevices. For example, in a video programming guide it is desirable topermit the channel information, program information, menus, and othernavigational and content related information to be read out (e.g., audiooutput) to the visually impaired person since they may have difficultyviewing the content or otherwise are unable to view the content becauseof blindness.

Existing video programming guides were developed in a manner to mosteffectively present the information contained therein for visualinspection (e.g., not for those who are blind or visually impaired). Asa result, simply including a text-to-speech conversion tends to resultin a generally inferior experience for the blind or visually impaired.For example, if the text of the programming guide includes “C C C” itmay be read out as “C” “C” “C”, but in many cases it would be preferableto read this out as “Triple C” for a more natural presentation.Similarly the pronunciation of foreign language text when usingtext-to-speech coversion may not be accurate. As an example the text“Les Miserables” would likely not be pronounced correctly with atraditional text-to-speech conversion. In this manner, it is desirableto include suitable information within the environment of the videoprogramming guide that enables the device to select a more appropriatemanner of providing the content contained therein to the blind and/orvisually impaired. In other cases, especially with proper names andforeign words (e.g., words not geographically local to the design of thedevice, such as a device developed for the United States marketpronouncing words written in French) manner in which the words arespoken may be difficult, at best, to understand. While suchfunctionality may be included within the device to facilitate suchlimitations, the implementation of such functionality should beundertaken in a manner that does not introduce additional limitations orambiguities. These functions may be implemented in any suitableenvironment, such as the environment illustrated in the enclosedfigures.

Thus instead of only using text-to-speech coversion, informationregarding pronunciation of words or sentences included in the serviceguide can be signalled within the service guide. This results in makingthe service guide information accessible. For example, reading out theservice guide content names/descriptions using the signalledpronunciation information may be helpful for a visually impaired user.The information regarding pronunciation of words or sentences may bereferred to as speech/phonetic information. The words “speechinformation”, “phonetic information” and “speech/phonetic information”are used interchangeably.

In general, the speech/phonetic information may be signalled byincluding a reference in the service guide with the reference pointingto the speech/phonetic information (e.g. a URL/URI pointing to speechdata) or by directly embedding the speech/phonetic information data inthe service guide.

In one embodiment, the speech information may be signaled inside one ormore fragments of OMA BCAST service guide. In particular, it may besignaled inside ‘Content’ fragment and/or ‘Service’ fragment and/or‘PreviewData’ fragment and/or ‘Purchase Item’ fragment and/or ‘PurchaseData’ fragment and/or ‘Purchase Channel’ fragment.

In one embodiment, the speech information may be signaled usingelements, sub-elements, and/or attributes as shown in FIG. 5.

In another embodiment the speech information could be signaled usingelements, sub-elements and attributes as shown in FIG. 5A. In FIG. 5Athe speech information related elements, sub-elements and attributes aresignaled inside the “Name” and “Description” elements of the “Service”fragment and “Content” fragment of OMA BCAST service guide. Thus the“Name” and “Description” elements are parents of these new elements.

In another embodiment, a CDATA (character data) restriction may be usedfor the embedded speech data (SpeechInfo element). This may be done forexample using a syntax where the embedded speech data is included inside<![CDATA[ . . . ]]> section. Since the embedded speech data may be amarkup data itself (e.g. SSML data) this allows including markup tagsinside this element without the XML parser parsing and interpretingthose as markup.

A constraint may be defined such that only one of speech information URL(e.g. SpeechInfoURI element) which points to externally specified speechinformation or embedded speech information data (e.g. SpeechInfoelement) may be specified when the speech object is of the same type.

This limitation may be included because if it is allowed to include boththe embedded speech information data (e.g. SpeechInfo element) and thespeech information URL (e.g. SpeechInfoURI element) which points toexternally specified speech information and if the type (e.g.content-type/mime-type) of both these elements is the same then thereceiving entity will not know which of the two to use for reading outthe pronunciation. To avoid this ambiguity, in this case, only one ofthe two elements is preferably allowed in the service guide data.

An exemplary example of this constraint is illustrated in FIG. 6 andFIG. 7.

Referring to FIG. 6, the service guide data includes a speechinformation URI A (e.g. SpeechInfoURI element) which has type (e.g.content-type/mime-type) equal to C. This URI A points to an externalspeech information object O which may for example reside on an externalserver. In this case, the type (e.g. content-type/mime-type) of thespeech information object O is equal to C (same as indicated in the typeattribute for Speech information URI element A).

Referring to FIG. 7, the service guide data includes an embedded speechinformation object B (e.g. SpeechInfo element) which has type (e.g.content-type/mime-type) equal to C. In this case, the type (e.g.content-type/mime-type) of the speech information object B is equal toC, same as indicated in the type attribute for Speech information URIelement in FIG. 6.

As a result with the constraint specified in this manner, the serviceguide can not include both the embedded speech information data (e.g.SpeechInfo element) and speech information URL (e.g. SpeechInfoURIelement) which points to externally specified speech informationelements.

In some embodiments, when the type (e.g. content-type/mime-type) of theembedded speech information data (e.g. SpeechInfo element) and speechinformation URL (e.g. SpeechInfoURI element) which points to externallyspecified speech information is different then both of these elementsmay be allowed to be present in the service guide. In this case thereceiving entity can make a decision regarding which one of the twoobjects to use based on its ability to handle particular type (e.g.content-type/mime-type) of data. This is illustrated in FIG. 8. In FIG.8 the service guide data includes a speech information URI U (e.g.SpeechInfoURI element) which has type (e.g. content-type/mime-type)equal to V. It also includes an embedded speech information object W(e.g. SpeechInfo element) which has type (e.g. content-type/mime-type)equal to X. In this case the type (e.g. content-type/mime-type) of thespeech information URI element (V) is not the same as (e.g.content-type/mime-type) the type of the embedded speech informationelement (X). It is also noted that the speech information URI A pointsto an external speech information object Y which may for example resideon an external server. In this case the type (e.g.content-type/mime-type) of the speech information object Y is equal to V(same as indicated in the type attribute for Speech information URIelement U).

A content-type attribute may be signaled for speech information URL andfor embedded speech information data elements.

The content-type attribute for speech information URL element may beoptional.

The content-type attribute for embedded speech information element maybe mandatory.

Instead of “type” attribute of any URI type, the content-type attributeof string type may be signaled for speech information URL element andfor embedded speech information element.

One of the purposes of the content-type attribute field may be todescribe the data type of the speech object referred by the URL and/orby the embedded. This knowledge may allow the receiving entity to selectan appropriate agent or mechanism to present the data to the user. Ingeneral, the data type of the speech object referred by the URL may beobtained by sending a request to that object. For example a HTTP GET orHTTP HEAD request may be sent. However sending such a request andgetting a response may add the latency. Thus including the content-typeof the speech object referred by the URL in the service guide mayquickly allow the receiving entity to know the type of data beingreferred. For example, if the receiving entity does not understand howto render data of a particular content-type as signaled by thecontent-type attribute value then it will not need to refer/send arequest to the external object. In one embodiment the semantics of theContent-Type header from RFC 2616 (HTTP) may be used as the semantic forthe attribute “content-type”.

In one embodiment: The semantics of content-type shall obey thesemantics of Content-Type header of HTTP/1.1 protocol RFC 2616.

In an alternative embodiment, an attribute “content-enc” may beoptionally signaled for embedded speech information data elements. Thisallows describing additional encoding applied to the embedded speechinformation object such as applying compression (e.g. gzip). Since thesize of embedded speech information data in ESG may be large socompressing it may be beneficial in reducing the size.

In one embodiment, the semantics of the Content-Encoding header from RFC2616 (HTTP) could be used as the semantic for the attribute“content-enc”.

In one embodiment: The semantics of content-enc shall obey the semanticsof Content-Encoding header of HTTP/1.1 protocol RFC 2616.

FIG. 9 illustrates the inclusion of content encoding related attributein addition to other speech information related elements and attributes.

In another embodiment the speech information could be signaled usingelements, sub-elements and attributes as shown in FIG. 9A. In FIG. 9Athe speech information related elements, sub-elements and attributes aresignaled inside the “Name” and “Description” elements of the “Service”fragment and “Content” fragment of OMA BCAST service guide. Thus the“Name” and “Description” elements are parents of these new elements.

In yet another embodiment, a single attribute content-type-enc may besignaled for speech information URL and for embedded speech informationdata elements as a whitespace separated concatenated string of‘content-type’ and ‘content-enc’ attributes with semantics and details,as described above. The content-type-enc attribute may be mandatory forspeech information URL element and may be mandatory for the embeddedspeech information element.

Also in this case the content-enc part of the string may be optional.

e.g. using ABNF notation: content-type-enc=content-type WSP(content-enc). Where WSP is white space and Augmented Backus-Naur Form(ABNF) is described in RFC 5234 (http://www.ietf.org/rfc/rfc5234.txt).

The cardinality of speech information URL (e.g. SpeechInfoURI element)which points to externally specified speech information may be equal to0 . . . 1, which means that zero or one such element may be present inthe service guide.

The cardinality of embedded speech information data (e.g. SpeechInfoelement) may be equal to 0 . . . 1, which means that zero or one suchelement may be present in the service guide.

This is because one speech information URI element and one embeddedspeech information element are sufficient to indicate the phoneticinformation as these elements can apply to the entire Name andDescription elements. Also when using SSML the elements such as<phoneme> element can already occur multiple times inside the SSML.

In another embodiment, the cardinality of some of the elements may bechanged from 0 . . . 1 to 0 . . . N only when the type (e.g.content-type/mime-type) of those elements are different. In this caseone or more of the following constraints may be defined:

The cardinality of speech information URL element (e.g. SpeechInfoURIelement) which points to externally specified speech information may beequal to 0 . . . N, which means that zero or more such elements may bepresent in the service guide if the ‘content-type’ of each of the speechinformation URL element (e.g. SpeechInfoURI element) is different.

In another embodiment, the constraint may be stated as:

When more than one speech information URL element (e.g. SpeechInfoURIelement) is present in the service guide, the value of ‘content-type’attribute of each of the speech information URL element (e.g.SpeechInfoURI element) may be different.

The cardinality of embedded speech information data element (e.g.SpeechInfo element) which points to externally specified speechinformation may be equal to 0 . . . N, which means that zero or moresuch elements may be present in the service guide if the ‘content-type’of each of the embedded speech information data element (e.g. SpeechInfoelement) is different.

In another embodiment, the constraint may be stated as:

When more than one embedded speech information data element (e.g.SpeechInfo element) is present in the service guide, the value of‘content-type’ attribute of each of the embedded speech information dataelement (e.g. SpeechInfo element) may be different.

The XML schema may be defined to syntactically restrict the presence ofonly one of the two elements: speech information URL element andembedded speech information data element.

An example XML schema for this is shown below:

List 1 <?xml version=″1.0″ encoding=″UTF-8″?> <xs:schemaxmlns:xs=″http://www.w3.org/2001/XMLSchema″>  <xs:elementname=″SpeechInfoObject″ type=″SpeechInfoType″/>  <xs:complexTypename=″SpeechInfoType″>   <xs:choice>    <xs:element name=″SpeechInfoURI″minOccurs=″0″    maxOccurs=″1″>     <xs:complexType>     <xs:simpleContent>       <xs:extension base=″xs:anyURI′′>       <xs:attribute name=″Type″ type=″xs:string″       use=″optional″/>       </xs:extension>      </xs:simpleContent>    </xs:complexType>    </xs:element>    <xs:element name=″SpeechInfo″minOccurs=′′0″ maxOccurs=″1″>     <xs:complexType>     <xs:simpleContent>       <xs:extension base=″xs:string″>       <xs:attribute name=″Type″ type=″xs:string″       use=″required″/>       </xs:extension>      </xs:simpleContent>    </xs:complexType>    </xs:element>   </xs:choice>  </xs:complexType></xs:schema>

Representation of such an XML schema to syntactically restrict thepresence of only one of the two elements: speech information URL elementand embedded speech information data element may be indicated as shownin FIG. 10.

In an alternative embodiment such a restriction may not be definedinside XML schema and the constraint may be simply imposed semantically.Thus either one of the following two constraints may be required:

Only one of the two elements: the speech information URL (e.g.SpeechInfoURI element) and embedded speech information data (e.g.SpeechInfo element) may be present.

In another embodiment this constraint may be stated as:

Only one of the two elements: the speech information URL (e.g.SpeechInfoURI element) and embedded speech information data (e.g.SpeechInfo element) shall be present inside a parent “Name” or“Description” element.

In another embodiment this constraint may be stated as:

Only one of the two elements: the SpeechInfoURI element and SpeechInfoelement shall be present inside a parent Name or Description element.

When the type (e.g. content-type/mime-type) of the speech informationURL (e.g. SpeechInfoURI element) and embedded speech information data(e.g. SpeechInfo element) is different (than each other) then both theseelements may be present in the service guide.

In another embodiment this constraint may be stated as:

When more than one speech information URL element (e.g. SpeechInfoURIelement) and embedded speech information data element (e.g. SpeechInfoelement) are present in the service guide, the value of ‘content-type’attribute of each of the speech information URL element (e.g.SpeechInfoURI element) and embedded speech information data element(e.g. SpeechInfo element) may be different.

In another embodiment this constraint may be stated as:

When more than one SpeechInfoURI element and SpeechInfo element arepresent inside a parent Name or Description element in the serviceguide, the value of Type/content-type attribute of each of theSpeechInfoURI element and SpeechInfo element shall be different.

In this case an example XML schema may be as shown below:

List 2 <?xml version=″1.0″ encoding=″UTF-8″?> <xs:schemaxmlns:xs=″http://www.w3.org/2001/XMLSchema″>  <xs:elementname=″SpeechInfoObject″ type=″SpeechInfoType″/>  <xs:complexTypename=″SpeechInfoType″>   <xs:all>    <xs:element name=″SpeechInfoURI″minOccurs=″0″    maxOccurs=″1″>     <xs:complexType>     <xs:simpleContent>       <xs:extension base=″xs:anyURI″>       <xs:attribute name=′′Type″ type=″xs:string″       use=″optional″/>       </xs:extension>      </xs:simpleContent>    </xs:complexType>    </xs:element>    <xs:element name=″SpeechInfo″minOccurs=″0″ maxOccurs=″1″>     <xs:complexType>     <xs:simpleContent>       <xs:extension base=″xs:string″>       <xs:attribute name=″Type″ type=″xs:string″       use=″required″/>       </xs:extension>      </xs:simpleContent>    </xs:complexType>    </xs:element>   </xs:all>  </xs:complexType></xs:schema>

In yet another embodiment the cardinality of elements may be relaxedfurther.

In this case an example XML schema may be as shown below:

List 3 <?xml version=″1.0″ encoding=″UTF-8″?> <xs:schemaxmlns:xs=″http://www.w3.org/2001/XMLSchema″>  <xs:elementname=″SpeechInfoObject″ type=″SpeechInfoType″/>  <xs:complexTypename=″SpeechInfoType″>   <xs:sequence>    <xs:elementname=″SpeechInfoURI″ minOccurs=″0″ maxOccurs=′′unbounded″>    <xs:complexType>      <xs:simpleContent>       <xs:extensionbase=″xs:anyURI″>        <xs:attribute name=″Type″ type=″xs:string″       use=″optional″/>       </xs:extension>      </xs:simpleContent>    </xs:complexType>    </xs:element>    <xs:element name=″SpeechInfo″minOccurs=0′′ maxOccurs=″unbounded″>     <xs:complexType>     <xs:simpleContent>       <xs:extension base=″xs:string″>       <xs:atttribute name=″Type″ type=″xs:string″       use=″required″/>       </xs:extension>      </xs:simpleContent>    </xs:complexType>    </xs:element>   </xs:sequence> </xs:complexType> </xs:schema>

Additional embodiments for signaling the speech/phonetic informationusing elements, sub-elements, and/or attributes may be included.

Information regarding pronunciation of words or sentences included inthe service guide can be signalled within service guide. This can behelpful in making the service guide information accessible. For examplereading out the service guide content names/descriptions using thesignalled pronunciation information may be helpful for visually impaireduser. The information regarding pronunciation of words or sentences willbe referred to as speech/phonetic information.

In general it is useful to include the speech/phonetic information byincluding a reference in service guide with the reference pointing tothe speech/phonetic information (e.g. a URL/URI pointing to speech data)or by directly embedding the speech/phonetic information data in theservice guide.

In one embodiment the speech information could be signaled inside one ormore fragments of OMA BCAST service guide. In particular it may besignaled inside ‘Content’ fragment and/or ‘Service’ fragment and/or‘PreviewData’ fragment and/or ‘Purchase Item’ fragment and/or ‘PurchaseData’ fragment and/or ‘Purchase Channel’ fragment.

In one embodiment the speech information could be signaled usingelements, sub-elements and attributes as shown in table 1 (SpeechPhonetic Information Extensions) below.

Elements Name and Description elements from OMA BCAST service fragmentare extended with addition of sub-elements and attributes related tospeech phonetic information, as listed in Table 1: Speech PhoneticInformation Extensions.

TABLE 1 Speech Phonetic Information Extensions Cardi- Data Name TypeCategory nality Description Type Name E1 NM/TM 0 . . . N Name of theService, possibly in String multiple languages. The language isexpressed using built-in XML attribute ‘xml:lang’ with this element.Contains the following elements: SpeechInfoURI SpeechInfo SpeechInfoURIE2 NM/TM 0 . . . N The URI address where SpeechInfo anyURI object forparent Name element is acquired. Speech file may be encoded in SSMLformat (http://www.w3.org/TR/speech- synthesis11/) or similar types ofmark up languages. Contains following attribute: content-typecontent-enc Content-type A NM/TM 0 . . . 1 Content-type of SpeechInfoobject String referenced by SpeechInfoURI. Content-enc A NM/TM 0 . . . 1Content encoding of SpeechInfo object String referenced bySpeechInfoURI. SpeechInfo E2 NM/TM 0 . . . N Embedded Speech informationobject anyURI for parent Name element. Contains following attribute:content-type content-enc Content-type A NM/TM 0 . . . 1 Content-type ofSpeechInfo object. String Content-enc A NM/TM 0 . . . 1 Content encodingof SpeechInfo object. String Description E1 NM/TM 0 . . . N Description,possibly in multiple String languages. The language is expressed usingbuilt-in XML attribute ‘xml:lang’ with this element. Contains thefollowing elements: SpeechInfoURI SpeechInfo SpeechInfoURI E2 NM/TM 0 .. . N The URI address where SpeechInfo anyURI object for parent Nameelement is acquired. Speech file may be encoded in SSML format(http://www.w3.org/TR/speech- synthesis11/) or similar types of mark uplanguages. Contains following attribute: content-type content-encContent-type A NM/TM 0 . . . 1 Content-type of SpeechInfo object Stringreferenced by SpeechInfoURI. Content-enc A NM/TM 0 . . . 1 Contentencoding of SpeechInfo object String referenced by SpeechInfoURLSpeechInfo E2 NM/TM 0 . . . N Embedded Speech information object anyURIfor parent Name element. Contains following attribute: content-typecontent-enc Content-type A NM/TM 0 . . . 1 Content-type of SpeechInfoobject. String Content-enc A NM/TM 0 . . . 1 Content encoding ofSpeechInfo object. String

Additionally one or more of the following constraints apply.

When more than one SpeechInfoURI element and SpeechInfo element arepresent inside a parent Name or Description element in the serviceguide, the value of content-type attribute of each of the SpeechInfoURIelement and SpeechInfo element shall be different.

The semantics of content-type attribute for SpeechInfoURI element andSpeechInfo element shall obey the semantics of Content-Type header ofHTTP/1.1 protocol RFC 2616.

When the content-type attribute is not present for SpeechInfoURI elementor SpeechInfo element it is inferred to have a value of“application/ssml+xml” for that element.

The semantics of content-enc attribute for SpeechInfoURI element andSpeechInfo element shall obey the semantics of Content-Encoding headerof HTTP/1.1 protocol RFC 2616.

When the content-enc attribute is not present for SpeechInfoURI elementor SpeechInfo element the associated speech information object for thecorresponding SpeechInfoURI element or SpeechInfo is assumed to have noadditional content encoding applied.

In another embodiment when the content-enc attribute is not present forSpeechInfoURI element or SpeechInfo element it is inferred to have avalue of “identity” for that element.

In another embodiment one or more of the following may apply.

When the content-type attribute is not present for SpeechInfoURI elementit is inferred to have a value of “application/ssml+xml” for thatelement.

When the content-type attribute is not present for SpeechInfo element itis inferred to have a value of “application/ssml+xml” for that element.

In other embodiments instead of “application/ssml+xml” the default valuefor the content-type attribute when not present may be inferred to besome other value such as either “application/voicexml+xml”, or“application/srgs”, “application/srgs+xml”, “application/ccxml+xml”, and“application/pls+xml”, or “text/ssml+xml”, or some other media typevalue defined inhttp://www.iana.org/assignments/media-types/media-types.xhtml or someother value.

When the content-enc attribute is not present for SpeechInfoURI elementthe associated speech information object is assumed to have noadditional content encoding applied.

When the content-enc attribute is not present for SpeechInfo element theassociated speech information object is assumed to have no additionalcontent encoding applied.

When the content-enc attribute is not present for SpeechInfoURI elementit is inferred to have a value of “identity” for that element.

When the content-enc attribute is not present for SpeechInfo element itis inferred to have a value of “identity” for that element.

In one embodiment the speech information could be additionally signaledusing elements, sub-elements and attributes as shown in table 2 below.

Elements Name and Description elements from service fragment areextended with addition of sub-elements and attributes related to speechphonetic information, as listed in, as listed in Table 2 Speech PhoneticInformation Extensions.

TABLE 2 Speech Phonetic Information Extensions Cardi- Data Name TypeCategory nality Description Type Name E1 NM/TM 0 . . . N Name of the‘Content’ fragment, String possibly in multiple languages. The languageis expressed using built-in XML attribute ‘xml:lang’ with this element.Contains the following elements: SpeechInfoURI SpeechInfo SpeechInfoURIE2 NM/TM 0 . . . N The URI address where SpeechInfo anyURI object forparent Name element is acquired. Speech file may be encoded in SSMLformat (http://www.w3.org/TR/speech- synthesis11/) or similar types ofmark up languages. Contains following attribute: content-typecontent-enc Content-type A NM/TM 0 . . . 1 Content-type of SpeechInfoobject String referenced by SpeechInfoURI. Content-enc A NM/TM 0 . . . 1Content encoding of SpeechInfo object String referenced bySpeechInfoURI. SpeechInfo E2 NM/TM 0 . . . N Embedded Speech informationobject anyURI for parent Name element. Contains following attribute:content-type content-enc Content-type A NM/TM 0 . . . 1 Content-type ofSpeechInfo object. String Content-enc A NM/TM 0 . . . 1 Content encodingof SpeechInfo object. String Description E1 NM/TM 0 . . . N Description,possibly in multiple String languages. The language is expressed usingbuilt-in XML attribute ‘xml:lang’ with this element. Contains thefollowing elements: SpeechInfoURI SpeechInfo SpeechInfoURI E2 NM/TM 0 .. . N The URI address where SpeechInfo anyURI object for parent Nameelement is acquired. Speech file may be encoded in SSML format(http://www.w3.org/TR/speech- synthesis11/) or similar types of mark uplanguages. Contains following attribute: content-type content-encContent-type A NM/TM 0 . . . 1 Content-type of SpeechInfo object Stringreferenced by SpeechInfoURI. Content-enc A NM/TM 0 . . . 1 Contentencoding of SpeechInfo object String referenced by SpeechInfoURI.SpeechInfo E2 NM/TM 0 . . . N Embedded Speech information object anyURIfor parent Name element. Contains following attribute: content-typecontent-enc Content-type A NM/TM 0 . . . 1 Content-type of SpeechInfoobject. String Content-enc A NM/TM 0 . . . 1 Content encoding ofSpeechInfo object. String

Additionally one or more of the following constraints may apply.

When more than one SpeechInfoURI element and SpeechInfo element arepresent inside a parent Name or Description element in the serviceguide, the value of content-type attribute of each of the SpeechInfoURIelement and SpeechInfo element shall be different.

The semantics of content-type attribute for SpeechInfoURI element andSpeechInfo element shall obey the semantics of Content-Type header ofHTTP/1.1 protocol RFC 2616.

When the content-type attribute is not present for SpeechInfoURI elementor SpeechInfo element it is inferred to have a value of“application/ssml+xml” for that element.

The semantics of content-enc attribute for SpeechInfoURI element andSpeechInfo element shall obey the semantics of Content-Encoding headerof HTTP/1.1 protocol RFC 2616.

When the content-enc attribute is not present for SpeechInfoURI elementor SpeechInfo element the associated speech information object for thecorresponding SpeechInfoURI element or SpeechInfo is assumed to have noadditional content encoding applied.

In another embodiment when the content-enc attribute is not present forSpeechInfoURI element or SpeechInfo element it is inferred to have avalue of “identity” for that element.

In another embodiment one or more of the following may apply.

When the content-type attribute is not present for SpeechInfoURI elementit is inferred to have a value of “application/ssml+xml” for thatelement.

When the content-type attribute is not present for SpeechInfo element itis inferred to have a value of “application/ssml+xml” for that element.

In other embodiments instead of “application/ssml+xml” the default valuefor the content-type attribute when not present may be inferred to besome other value such as either “application/voicexml+xml”, or“application/srgs”, “application/srgs+xml”, “application/ccxml+xml”, and“application/pls+xml”, or “text/ssml+xml”, or some other media typevalue defined inhttp://www.iana.org/assignments/media-types/media-types.xhtml or someother value.

When the content-enc attribute is not present for SpeechInfoURI elementthe associated speech information object is assumed to have noadditional content encoding applied.

When the content-enc attribute is not present for SpeechInfo element theassociated speech information object is assumed to have no additionalcontent encoding applied.

When the content-enc attribute is not present for SpeechInfoURI elementit is inferred to have a value of “identity” for that element.

When the content-enc attribute is not present for SpeechInfo element itis inferred to have a value of “identity” for that element.

In another embodiment the following may apply. The speech informationcould be signaled using elements, sub-elements and attributes as shownin table 3 below. Elements Name and Description elements from OMA BCASTservice fragment are extended with addition of sub-elements andattributes related to speech phonetic information, as listed in Table 1:Speech Phonetic Information Extensions. Each of the Name and Descriptionelements include a text attribute which provides the name anddescription respectively. Language of the text attribute is expressedwith XML attribute ‘xml:lang’.

TABLE 3 Speech Phonetic Information Extensions Cardi- Data Name TypeCategory nality Description Type Name E1 NM/TM 0 . . . N Extended Nameelement which includes sub-elements to indicate name and phoneticinformation about name. Contains the following elements: SpeechInfoURISpeechInfo Contains following attributes: text xml:lang text A NM/TM 1Name of the Service. string xml:lang A NM/TM 0 . . . 1 The language ofthe text attribute string expressed with XML attribute ‘xml:lang’SpeechInfoURI E2 NM/TM 0 . . . N The URI address where SpeechInfo anyURIobject for parent Name element is acquired. Speech file may be encodedin SSML format (http://www.w3.org/TR/speech- synthesis11/) or similartypes of mark up languages. Contains following attribute: content-typecontent-enc Content-type A NM/TM 0 . . . 1 Content-type of SpeechInfoobject String referenced by SpeechInfoURI. Content-enc A NM/TM 0 . . . 1Content encoding of SpeechInfo object String referenced bySpeechInfoURI. SpeechInfo E2 NM/TM 0 . . . N Embedded Speech informationobject anyURI for parent Name element. Contains following attribute:content-type content-enc Content-type A NM/TM 0 . . . 1 Content-type ofSpeechInfo object. String Content-enc A NM/TM 0 . . . 1 Content encodingof SpeechInfo object. String Description E1 NM/TM 0 . . . N ExtendedDescription element which includes sub-elements to indicate descriptionand phonetic information about description. Contains the followingelements: SpeechInfoURI SpeechInfo Contains following attributes: textxml:lang text A NM/TM 1 Description of the Service. string xml:lang ANM/TM 0 . . . 1 The language of the text attribute string expressed withXML attribute ‘xml:lang’ SpeechInfoURI E2 NM/TM 0 . . . N The URIaddress where SpeechInfo anyURI object for parent Name element isacquired. Speech file may be encoded in SSML format(http://www.w3.org/TR/speech- synthesis11/) or similar types of mark uplanguages. Contains following attribute: content-type content-encContent-type A NM/TM 0 . . . 1 Content-type of SpeechInfo object Stringreferenced by SpeechInfoURI. Content-enc A NM/TM 0 . . . 1 Contentencoding of SpeechInfo object String referenced by SpeechInfoURI.SpeechInfo E2 NM/TM 0 . . . N Embedded Speech information object anyURIfor parent Name element. Contains following attribute: content-typecontent-enc Content-type A NM/TM 0 . . . 1 Content-type of SpeechInfoobject. String Content-enc A NM/TM 0 . . . 1 Content encoding ofSpeechInfo object. String

Additionally one or more of the following constraints may apply.

When more than one SpeechInfoURI element and SpeechInfo element arepresent inside a parent Name or Description element in the serviceguide, the value of content-type attribute of each of the SpeechInfoURIelement and SpeechInfo element shall be different.

The semantics of content-type attribute for SpeechInfoURI element andSpeechInfo element shall obey the semantics of Content-Type header ofHTTP/1.1 protocol RFC 2616.

When the content-type attribute is not present for SpeechInfoURI elementor SpeechInfo element it is inferred to have a value of“application/ssml+xml” for that element.

The semantics of content-enc attribute for SpeechInfoURI element andSpeechInfo element shall obey the semantics of Content-Encoding headerof HTTP/1.1 protocol RFC 2616.

When the content-enc attribute is not present for SpeechInfoURI elementor SpeechInfo element the associated speech information object for thecorresponding SpeechInfoURI element or SpeechInfo is assumed to have noadditional content encoding applied.

In another embodiment when the content-enc attribute is not present forSpeechInfoURI element or SpeechInfo element it is inferred to have avalue of “identity” for that element.

In another embodiment one or more of the following may apply:

When the content-type attribute is not present for SpeechInfoURI elementit is inferred to have a value of “application/ssml+xml” for thatelement.

When the content-type attribute is not present for SpeechInfo element itis inferred to have a value of “application/ssml+xml” for that element.

In other embodiments instead of “application/ssml+xml” the default valuefor the content-type attribute when not present may be inferred to besome other value such as either “application/voicexml+xml”, or“application/srgs”, “application/srgs+xml”, “application/ccxml+xml”, and“application/pls+xml”, or “text/ssml+xml”, or some other media typevalue defined inhttp://www.iana.org/assignments/media-types/media-types.xhtml or someother value.

When the content-enc attribute is not present for SpeechInfoURI elementthe associated speech information object is assumed to have noadditional content encoding applied.

When the content-enc attribute is not present for SpeechInfo element theassociated speech information object is assumed to have no additionalcontent encoding applied.

When the content-enc attribute is not present for SpeechInfoURI elementit is inferred to have a value of “identity” for that element.

When the content-enc attribute is not present for SpeechInfo element itis inferred to have a value of “identity” for that element.

In one embodiment the speech information could be additionally signaledusing elements, sub-elements and attributes as shown in table 4 below.

Elements Name and Description elements from service fragment areextended with addition of sub-elements and attributes related to speechphonetic information, as listed in, as listed in Table 2 Speech PhoneticInformation Extensions.

TABLE 4 Speech Phonetic Information Extensions Cardi- Data Name TypeCategory nality Description Type Name E1 NM/TM 0 . . . N Extended Nameelement which includes sub-elements to indicate name and phoneticinformation about name. Contains the following elements: SpeechInfoURISpeechInfo Contains following attributes: text xml:lang text A NM/TM 1Name of the ‘Content’ fragment. string xml:lang A NM/TM 0 . . . 1 Thelanguage of the text attribute string expressed with XML attribute‘xml:lang’ SpeechInfoURI E2 NM/TM 0 . . . N The URI address whereSpeechInfo anyURI object for parent Name element is acquired. Speechfile may be encoded in SSML format (http://www.w3.org/TR/speech-synthesis11/) or similar types of mark up languages. Contains followingattribute: content-type content-enc Content-type A NM/TM 0 . . . 1Content-type of SpeechInfo object String referenced by SpeechInfoURI.Content-enc A NM/TM 0 . . . 1 Content encoding of SpeechInfo objectString referenced by SpeechInfoURI. SpeechInfo E2 NM/TM 0 . . . NEmbedded Speech information object anyURI for parent Name element.Contains following attribute: content-type content-enc Content-type ANM/TM 0 . . . 1 Content-type of SpeechInfo object. String Content-enc ANM/TM 0 . . . 1 Content encoding of SpeechInfo object. StringDescription E1 NM/TM 0 . . . N Extended Description element whichincludes sub-elements to indicate description and phonetic informationabout description. Contains the following elements: SpeechInfoURISpeechInfo Contains following attributes: text xml:lang text A NM/TM 1Description of the Content. string xml:lang A NM/TM 0 . . . 1 Thelanguage of the text attribute string expressed with XML attribute‘xml:lang’ SpeechInfoURI E2 NM/TM 0 . . . N The URI address whereSpeechInfo anyURI object for parent Name element is acquired. Speechfile may be encoded in SSML format (http://www.w3.org/TR/speech-synthesis11/) or similar types of mark up languages. Contains followingattribute: content-type content-enc Content-type A NM/TM 0 . . . 1Content-type of SpeechInfo object String referenced by SpeechInfoURI.Content-enc A NM/TM 0 . . . 1 Content encoding of SpeechInfo objectString referenced by SpeechInfoURI. SpeechInfo E2 NM/TM 0 . . . NEmbedded Speech information object anyURI for parent Name element.Contains following attribute: content-type content-enc Content-type ANM/TM 0 . . . 1 Content-type of SpeechInfo object. String Content-enc ANM/TM 0 . . . 1 Content encoding of SpeechInfo object. String

Additionally one or more of the following constraints apply.

When more than one SpeechInfoURI element and SpeechInfo element arepresent inside a parent Name or Description element in the serviceguide, the value of content-type attribute of each of the SpeechInfoURIelement and SpeechInfo element shall be different.

The semantics of content-type attribute for SpeechInfoURI element andSpeechInfo element shall obey the semantics of Content-Type header ofHTTP/1.1 protocol RFC 2616.

When the content-type attribute is not present for SpeechInfoURI elementor SpeechInfo element it is inferred to have a value of“application/ssml+xml” for that element.

The semantics of content-enc attribute for SpeechInfoURI element andSpeechInfo element shall obey the semantics of Content-Encoding headerof HTTP/1.1 protocol RFC 2616.

When the content-enc attribute is not present for SpeechInfoURI elementor SpeechInfo element the associated speech information object for thecorresponding SpeechInfoURI element or SpeechInfo is assumed to have noadditional content encoding applied.

In another embodiment when the content-enc attribute is not present forSpeechInfoURI element or SpeechInfo element it is inferred to have avalue of “identity” for that element.

In another embodiment one or more of the following may apply.

When the content-type attribute is not present for SpeechInfoURI elementit is inferred to have a value of “application/ssml+xml” for thatelement.

When the content-type attribute is not present for SpeechInfo element itis inferred to have a value of “application/ssml+xml” for that element.

In other embodiments instead of “application/ssml+xml” the default valuefor the content-type attribute when not present may be inferred to besome other value such as either “application/voicexml+xml”, or“application/srgs”, “application/srgs+xml”, “application/ccxml+xml”, and“application/pls+xml”, or “text/ssml+xml”, or some other media typevalue defined inhttp://www.iana.org/assignments/media-types/media-types.xhtml or someother value.

When the content-enc attribute is not present for SpeechInfoURI elementthe associated speech information object is assumed to have noadditional content encoding applied.

When the content-enc attribute is not present for SpeechInfo element theassociated speech information object is assumed to have no additionalcontent encoding applied.

When the content-enc attribute is not present for SpeechInfoURI elementit is inferred to have a value of “identity” for that element.

When the content-enc attribute is not present for SpeechInfo element itis inferred to have a value of “identity” for that element.

In an alternative embodiment the speech information could be signaledusing elements, sub-elements and attributes as shown in table 5 below.

Elements Name and Description elements from OMA BCAST service fragmentare extended with addition of sub-elements and attributes related tospeech phonetic information as listed in Table 1: Speech PhoneticInformation Extensions. Each of the Name and Description elementsinclude a Text element which provides the name and descriptionrespectively.

TABLE 5 Speech Phonetic Information Extensions Cardi- Data Name TypeCategory nality Description Type Name E1 NM/TM 0 . . . N ExtendedContainer element which includes sub-elements to indicate name andphonetic information about name. Contains the following elements: TextSpeechInfoURI SpeechInfo Text E2 NM/TM 1 Name of the Service, possiblyin string multiple languages. The language is expressed using built-inXML attribute ‘xml:lang’ with this element. SpeechInfoURI E2 NM/TM 0 . .. N The URI address where SpeechInfo anyURI object for parent Nameelement is acquired. Speech file may be encoded in SSML format(http://www.w3.org/TR/speech- synthesis11/) or similar types of mark uplanguages. Contains following attribute: content-type content-encContent-type A NM/TM 0 . . . 1 Content-type of SpeechInfo object Stringreferenced by SpeechInfoURI. Content-enc A NM/TM 0 . . . 1 Contentencoding of SpeechInfo object String referenced by SpeechInfoURI.SpeechInfo E2 NM/TM 0 . . . N Embedded Speech information object anyURIfor parent Name element. Contains following attribute: content-typecontent-enc Content-type A NM/TM 0 . . . 1 Content-type of SpeechInfoobject. String Content-enc A NM/TM 0 . . . 1 Content encoding ofSpeechInfo object. String Description E1 NM/TM 0 . . . N ExtendedDescription element which includes sub-elements to indicate descriptionand phonetic information about description. Contains the followingelements: Text SpeechInfoURI SpeechInfo Text E2 NM/TM 1 Description,possibly in multiple string languages. The language is expressed usingbuilt-in XML attribute ‘xml:lang’ with this element. SpeechInfoURI E2NM/TM 0 . . . N The URI address where SpeechInfo anyURI object forparent Name element is acquired. Speech file may be encoded in SSMLformat (http://www.w3.org/TR/speech- synthesis11/) or similar types ofmark up languages. Contains following attribute: content-typecontent-enc Content-type A NM/TM 0 . . . 1 Content-type of SpeechInfoobject String referenced by SpeechInfoURI. Content-enc A NM/TM 0 . . . 1Content encoding of SpeechInfo object String referenced bySpeechInfoURI. SpeechInfo E2 NM/TM 0 . . . N Embedded Speech informationobject anyURI for parent Name element. Contains following attribute:content-type content-enc Content-type A NM/TM 0 . . . 1 Content-type ofSpeechInfo object. String Content-enc A NM/TM 0 . . . 1 Content encodingof SpeechInfo String object.

Additionally one or more of the following constraints may apply.

When more than one SpeechInfoURI element and SpeechInfo element arepresent inside a parent Name or Description element in the serviceguide, the value of content-type attribute of each of the SpeechInfoURIelement and SpeechInfo element shall be different.

The semantics of content-type attribute for SpeechInfoURI element andSpeechInfo element shall obey the semantics of Content-Type header ofHTTP/1.1 protocol RFC 2616.

When the content-type attribute is not present for SpeechInfoURI elementor SpeechInfo element it is inferred to have a value of“application/ssml+xml” for that element.

The semantics of content-enc attribute for SpeechInfoURI element andSpeechInfo element shall obey the semantics of Content-Encoding headerof HTTP/1.1 protocol RFC 2616.

When the content-enc attribute is not present for SpeechInfoURI elementor SpeechInfo element the associated speech information object for thecorresponding SpeechInfoURI element or SpeechInfo is assumed to have noadditional content encoding applied.

In another embodiment when the content-enc attribute is not present forSpeechInfoURI element or SpeechInfo element it is inferred to have avalue of “identity” for that element.

In another embodiment one or more of the following may apply.

When the content-type attribute is not present for SpeechInfoURI elementit is inferred to have a value of “application/ssml+xml” for thatelement.

When the content-type attribute is not present for SpeechInfo element itis inferred to have a value of “application/ssml+xml” for that element.

In other embodiments instead of “application/ssml+xml” the default valuefor the content-type attribute when not present may be inferred to besome other value such as either “application/voicexml+xml”, or“application/srgs”, “application/srgs+xml”, “application/ccxml+xml”, and“application/pls+xml”, or “text/ssml+xml”, or some other media typevalue defined inhttp://www.iana.org/assignments/media-types/media-types.xhtml or someother value.

When the content-enc attribute is not present for SpeechInfoURI elementthe associated speech information object is assumed to have noadditional content encoding applied.

When the content-enc attribute is not present for SpeechInfo element theassociated speech information object is assumed to have no additionalcontent encoding applied.

When the content-enc attribute is not present for SpeechInfoURI elementit is inferred to have a value of “identity” for that element.

When the content-enc attribute is not present for SpeechInfo element itis inferred to have a value of “identity” for that element.

In one embodiment the speech information could be additionally signaledusing elements, sub-elements and attributes as shown in table 6 below.

Elements Name and Description elements from service fragment areextended with addition of sub-elements and attributes related to speechphonetic information, as listed in, as listed in Table 2 Speech PhoneticInformation Extensions.

TABLE 6 Speech Phonetic Information Extensions Cardi- Data Name TypeCategory nality Description Type Name E1 NM/TM 0 . . . N Extended Nameelement which includes sub-elements to indicate name and phoneticinformation about name. Contains the following elements: TextSpeechInfoURI SpeechInfo Text E2 NM/TM 1 Name of the ‘Content’ fragment,string possibly in multiple languages. The language is expressed usingbuilt-in XML attribute ‘xml:lang’ with this element. SpeechInfoURI E2NM/TM 0 . . . N The URI address where SpeechInfo anyURI object forparent Name element is acquired. Speech file may be encoded in SSMLformat (http://www.w3.org/TR/speech- synthesis11/) or similar types ofmark up languages. Contains following attribute: content-typecontent-enc Content-type A NM/TM 0 . . . 1 Content-type of SpeechInfoobject String referenced by SpeechInfoURI. Content-enc A NM/TM 0 . . . 1Content encoding of SpeechInfo object String referenced bySpeechInfoURI. SpeechInfo E2 NM/TM 0 . . . N Embedded Speech informationobject anyURI for parent Name element. Contains following attribute:content-type content-enc Content-type A NM/TM 0 . . . 1 Content-type ofSpeechInfo object. String Content-enc A NM/TM 0 . . . 1 Content encodingof SpeechInfo object. String Description E1 NM/TM 0 . . . N ExtendedDescription element which includes sub-elements to indicate descriptionand phonetic information about description. Contains the followingelements: Text SpeechInfoURI SpeechInfo Text E2 NM/TM 1 Description,possibly in multiple string languages. The language is expressed usingbuilt-in XML attribute ‘xml:lang’ with this element. SpeechInfoURI E2NM/TM 0 . . . N The URI address where SpeechInfo anyURI object forparent Name element is acquired. Speech file may be encoded in SSMLformat (http://www.w3.org/TR/speech- synthesis11/) or similar types ofmark up languages. Contains following attribute: content-typecontent-enc Content-type A NM/TM 0 . . . 1 Content-type of SpeechInfoobject String referenced by SpeechInfoURI. Content-enc A NM/TM 0 . . . 1Content encoding of SpeechInfo object String referenced bySpeechInfoURI. SpeechInfo E2 NM/TM 0 . . . N Embedded Speech informationobject anyURI for parent Name element. Contains following attribute:content-type content-enc Content-type A NM/TM 0 . . . 1 Content-type ofSpeechInfo object. String Content-enc A NM/TM 0 . . . 1 Content encodingof SpeechInfo object. String

Additionally one or more of the following constraints may apply.

When more than one SpeechInfoURI element and SpeechInfo element arepresent inside a parent Name or Description element in the serviceguide, the value of content-type attribute of each of the SpeechInfoURIelement and SpeechInfo element shall be different.

The semantics of content-type attribute for SpeechInfoURI element andSpeechInfo element shall obey the semantics of Content-Type header ofHTTP/1.1 protocol RFC 2616.

When the content-type attribute is not present for SpeechInfoURI elementor SpeechInfo element it is inferred to have a value of“application/ssml+xml” for that element.

The semantics of content-enc attribute for SpeechInfoURI element andSpeechInfo element shall obey the semantics of Content-Encoding headerof HTTP/1.1 protocol RFC 2616.

When the content-enc attribute is not present for SpeechInfoURI elementor SpeechInfo element the associated speech information object for thecorresponding SpeechInfoURI element or SpeechInfo is assumed to have noadditional content encoding applied.

In another embodiment when the content-enc attribute is not present forSpeechInfoURI element or SpeechInfo element it is inferred to have avalue of “identity” for that element.

In another embodiment one or more of the following may apply.

When the content-type attribute is not present for SpeechInfoURI elementit is inferred to have a value of “application/ssml+xml” for thatelement.

When the content-type attribute is not present for SpeechInfo element itis inferred to have a value of “application/ssml+xml” for that element.

In other embodiments instead of “application/ssml+xml” the default valuefor the content-type attribute when not present may be inferred to besome other value such as either “application/voicexml+xml”, or“application/srgs”, “application/srgs+xml”, “application/ccxml+xml”, and“application/pls+xml”, or “text/ssml+xml”, or some other media typevalue defined inhttp://www.iana.org/assignments/media-types/media-types.xhtml or someother value.

When the content-enc attribute is not present for SpeechInfoURI elementthe associated speech information object is assumed to have noadditional content encoding applied.

When the content-enc attribute is not present for SpeechInfo element theassociated speech information object is assumed to have no additionalcontent encoding applied.

When the content-enc attribute is not present for SpeechInfoURI elementit is inferred to have a value of “identity” for that element.

When the content-enc attribute is not present for SpeechInfo element itis inferred to have a value of “identity” for that element.

XML Schema may be used for speech information object signaling. In oneembodiment XML schema shown below in “Table: XML schema A” is used. Insome cases this may correspond to Table 1 and Table 2. Representation ofsuch an XML schema may be indicated as shown in FIG. 11.

TABLE XML schema A List 4 <?xml version=″1.0″ encoding=″UTF-8″?><xs:schema xmlns:xs=″http://www.w3.org/2001/XMLSchema″>  <xs:elementname=″SpeechInfoObject″ type=″SpeechInfoType″/>  <xs:complexTypename=″SpeechInfoType″>   <xs:sequence>    <xs:elementname=″SpeechInfoURI″ minOccurs=″0″ maxOccurs=′′unbounded″>    <xs:complexType>      <xs:simpleContent>       <xs:extensionbase=″xs:anyURI″>        <xs:attribute name=″content-type″type=″xs:string″ use=″optional″/>        <xs:attributename=′′content-enc″ type=″xs:string″ use=″optional″/>      </xs:extension>      </xs:simpleContent>     </xs:complexType>   </xs:element>    <xs:element name=′′SpeechInfo″ minOccurs=″0″maxOccurs=″unbounded″>     <xs:complexType>      <xs:simpleContent>      <xs:extension base=″xs:string″>        <xs:attributename=″content-type″ type=″xs:string′′ use=″optional″/>       <xs:attribute name=″content-enc″ type=″xs:string″use=″optional″/>       </xs:extension>      </xs:simpleContent>    </xs:complexType>    </xs:element>   </xs:sequence> </xs:complexType> </xs:schema>

In an alternative embodiment some of the use=‘optional’ may be changedto use=‘required’.

In an alternative embodiment XML schema shown below in “Table: XMLschema B” is used. In some cases this may correspond to Table 3 andTable 4. Representation of such an XML schema may be indicated as shownin FIG. 12.

TABLE XML schema B List 5-1 <?xml version=″1.0″ encoding=″UTF-8″?><xs:schema xmlns:xs=″http://www.w3.org/2001/XMLSchema″> <xs:importnamespace=′′http://www.w3.org/XML/1998/namespace″schemaLocation=″http://www.w3.org/2001/xml.xsd″/> <xs:complexTypename=″ServiceType″>       <xs:sequence>         <xs:element name=″Name′′type=″NameDescriptionType″ minOccurs=″0″ maxOccurs=″unbounded″/>        <xs:element name=″Description″ type=′′NameDescriptionType″minOccurs=″0″ maxOccurs=″unbounded″/>      </xs:sequence></xs:complexType> <xs:complexType name=″ContentType″>      <xs:sequence>         <xs:element name=″Name″type=″NameDescriptionType″ minOccurs=″0″ maxOccurs=″unbounded″/>        <xs:element name=″Description″ type=″NameDescriptionType″minOccurs=″0″ maxOccurs=″unbounded″/>      </xs:sequence></xs:complexType> List 5-2  <xs:complexType name=″NameDescriptionType″>  <xs:sequence>    <xs:element name=″SpeechInfoURI″ minOccurs=″0″maxOccurs=″unbounded″>     <xs:complexType>      <xs:simpleContent>       <xs:extension base-″xs:anyURI″>          <xs:attributename=″content-type″ type=″xs:string″ use=″optional″/>         <xs:attribute name=″content-enc″ type=″xs:string″use=″optional″/>        </xs:extension>      </xs:simpleContent>    </xs:complexType>    </xs:element>    <xs:element name=″SpeechInfo″minOccurs=″0″ maxOccurs=″unbounded″>     <xs:complexType>     <xs:simpleContent>       <xs:extension base=″xs:string″>         <xs:attribute name=″content-type″ type=″xs:string″use=″optional″/>          <xs:attribute name=″content-enc″type=″xs:string″ use=″optional″/>       </xs:extension>     </xs:simpleContent>     </xs:complexType>    </xs:element>  </xs:sequence>   <xs:attribute name=″text″ type=″xs:string″use=″required″ />   <xs:attribute ref=″xml:lang″ use=″optional″/></xs:complexType> </xs:schema>

In an alternative embodiment XML schema shown below in “Table: XMLschema C” is used. In some cases this may correspond to Table 5 andTable 6. Representation of such an XML schema may be indicated as shownin FIG. 13.

TABLE XML schema C List 6-1 <?xml version=″1.0″ encoding=″UTF-8″?><xs:schema xmlns:xs=″http://www.w3.org/2001/XMLSchema″> <xs:importnamespace=″http://www.w3.org/XML/1998/namespace″schemaLocation=″http://www.w3.org/2001/xml.xsd″/> <xs:complexTypename=″ServiceType″>      <xs:sequence>       <xs:element name=″Name″type=″NameDescriptionType″ minOccurs=″0″ maxOccurs=″unbounded″/>      <xs:element name=″Description″ type=″NameDescriptionType″minOccurs=″0″ maxOccurs=″unbounded″/>   </xs:sequence> </xs:complexType><xs:complexType name=″ContentType″>      <xs:sequence>       <xs:elementname=″Name″ type=″NameDescriptionType″ minOccurs=″0″maxOccurs=″unbounded″/>       <xs:element name=″Description″type=″NameDescriptionType′′ minOccurs=″0″ maxOccurs=″unbounded″/>  </xs:sequence> </xs:complexType> List 6-2  <xs:complexTypename=″NameDescriptionType″>   <xs:sequence>    <xs:element name=″Text″>    <xs:complexType>      <xs:simpleContent>       <xs:extensionbase=″xs:string″>        <xs:attribute ref=″xml:lang″ use=″optional″/>      </xs:extension>      </xs:simpleContent>     </xs:complexType>   </xs:element>    <xs:element name=″SpeechInfoURI″ minOccurs=″0″maxOccurs=″unbounded′′>     <xs:complexType>      <xs:simpleContent>      <xs:extension base=″xs:anyURI″>        <xs:attributename=″content-type″ type=″xs:string″ use=″optional″/>       <xs:attribute name=″content-enc″ type=″xs:string″use=″optional″/>       </xs:extension>      </xs:simpleContent>    </xs:complexType>    </xs:element>    <xs:element name=″SpeechInfo″minOccurs=″0″ maxOccurs=″unbounded″>     <xs:complexType>     <xs:simpleContent>       <xs:extension base=″xs:string″>       <xs:attribute name=″content-type″ type=″xs:string″use=″optional″/>        <xs:attribute name=″content-enc″type=″xs:string″ use=″optional″/>       </xs:extension>     </xs:simpleContent>     </xs:complexType>    </xs:element>  </xs:sequence> </xs:complexType> </xs:schema>

In yet another embodiment <!--Name and Description elements in Serviceand Content Fragments of OMA BCAST service guide will be replaced withfollowing extended elements-->

<xs:element name=“Name” type=“NameDescriptionType” minOccurs=“0”maxOccurs=“unbounded”/>

<xs:element name=“Description” type=“NameDescriptionType” minOccurs=“0”maxOccurs=“unbounded”/>

In some embodiments some of the elements above may be changed from E2 toE1.

In some embodiments the cardinality of some of the elements may bechanged. For example cardinality may be changed from “1” to “1 . . . N”or cardinality may be changed from “1” to “0 . . . N” or cardinality maybe changed from “1” to “0 . . . 1” or cardinality may be changed from “0. . . 1” to “0 . . . N” or cardinality may be changed from “0 . . . N”to “0 . . . 1”.

In some embodiments some of the elements could instead be signalled asattributes.

In some embodiments some of the attributes could instead be signalled aselements.

In another embodiments some of the “NM/TM” values in the “category” maybe changed to “NM/TO” or “NO/TM” or “NO/TO”.

In some embodiments instead of XML some other format e.g.JSON/CSV/BNF/ABNF/EBNF may be used for representing the same informationconveyed in the XML format.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the systems, methods, and apparatus described herein withoutdeparting from the scope of the claims.

The invention claimed is:
 1. A method for decoding a service guideassociated with a video bitstream comprising: (a) receiving a contentfragment within the service guide; (b) receiving a name element withinthe content fragment, wherein the name element is an extended nameelement which includes sub-elements to indicate name and phoneticinformation about the name element, where a first one of thesub-elements is a SpeechInfoURI element and a second one of thesub-elements is a SpeechInfo element; (c) determining if a firstcontent-type attribute is present in the SpeechInfoURI element; (d)receiving the first content type attribute in the SpeechInfoURI elementif the first content-type attribute is present in the SpeechInfoURIelement; (e) setting the first content-type attribute to a first valueif the first content-type attribute is not present in the SpeechInfoURIelement; (f) determining if a second content-type attribute is presentin the SpeechInfo element; (g) receiving the second content-typeattribute in the SpeechInfo element if the second content-type attributeis present in the SpeechInfo element; (h) setting the secondcontent-type attribute to the first value if the second content-typeattribute is not present in the SpeechInfo element; and (i) decoding theservice guide.
 2. The method of claim 1 wherein the first content-typeattribute indicates a content-type of a SpeechInfoobject referenced bythe SpeechInfoURI element.
 3. The method of claim 1 wherein the secondcontent-type attribute is a content-type of an embedded speechinformation object.
 4. The method of claim 1 wherein the first value is“application/ssml+xml”.
 5. A method for decoding a service guideassociated with a video bitstream comprising: (a) receiving a contentfragment within the service guide; (b) receiving a name element withinthe content fragment, wherein the name element is an extended nameelement which includes sub-elements to indicate name and phoneticinformation about the name element, where a first one of thesub-elements is a SpeechInfoURI element and a second one of thesub-elements is a SpeechInfo element; (c) determining if a firstcontent-enc attribute is present in the SpeechInfoURI element; (d)receiving the first content-enc attribute in the SpeechInfoURI elementif the first content-enc attribute is present in the SpeechInfoURIelement; (e) setting the first content-enc attribute to a first value ifthe first content-enc attribute is not present in the SpeechInfoURIelement; (f) determining if a second content-enc attribute is present inthe SpeechInfo element; (g) receiving the second content-enc attributein the SpeechInfo element if the second content-enc attribute is presentin the SpeechInfo element; (h) setting the second content-enc attributeto the first value if the second content-enc attribute is not present inthe SpeechInfo element; and (i) decoding the service guide.
 6. Themethod of claim 5 wherein the first content-enc attribute indicates acontent-type of a SpeechInfoobject referenced by the SpeechInfoURIelement.
 7. The method of claim 5 wherein the second content-encattribute is a content-type of an embedded speech information.
 8. Themethod of claim 5, wherein the first value is “application/ssml+xml”. 9.A device for decoding a service guide associated with a video bitstream,the device comprising: a memory; and a processor, wherein the processorconfigured to perform steps of: (a) receiving a content fragment withinthe service guide; (b) receiving a name element within the contentfragment, wherein the name element is an extended name element whichincludes sub-elements to indicate name and phonetic information aboutthe name element, where a first one of the sub-elements is aSpeechInfoURI element and a second one of the sub-elements is aSpeechInfo element; (c) determining if a first content-type attribute ispresent in the SpeechInfoURI element; (d) receiving the first contenttype attribute in the SpeechInfoURI element if the first content-typeattribute is present in the SpeechInfoURI element; (e) setting the firstcontent-type attribute to a first value if the first content-typeattribute is not present in the SpeechInfoURI element; (f) determiningif a second content-type attribute is present in the SpeechInfo element;(g) receiving the second content-type attribute in the SpeechInfoelement if the second content-type attribute is present in theSpeechInfo element; (h) setting the second content-type attribute to thefirst value if the second content-type attribute is not present in theSpeechInfo element; and (i) decoding the service guide.